Applies ToWindows 7 Enterprise Windows 7 Professional Windows 7 Ultimate Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Standard Windows HPC Server 2008 R2

Symptoms

In an Active Directory domain network environment, you apply a "Desktop Wallpaper" Group Policy setting to the domain users. However, the setting is not applied to domain users who log on to client computers that are running Windows 7 or Windows Server 2008 R2.This issue varies if the following conditions are true:

  • If the domain user logs on the domain after you deploy the "Desktop Wallpaper" Group Policy setting, the desktop background changes to black. Note The color of the desktop background varies, depending on the color scheme that you set.

  • If the domain user logs on the domain before you apply the "Desktop Wallpaper" Group Policy setting, the desktop background does not change.

Additionally, in the Personalization window of the client computer, the desktop background is displayed as being changed to the setting that you applied. Note For more information about how to apply a "Desktop Wallpaper" Group Policy setting, see the More Information section.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 7 or Windows Server 2008 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7

File name

File version

File size

Date

Time

Platform

Shell32.dll

6.1.7600.20600

12,866,560

19-Dec-2009

09:10

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Shell32.dll

6.1.7600.20600

14,162,432

19-Dec-2009

10:12

x64

Shell32.dll

6.1.7600.20600

12,866,560

19-Dec-2009

09:10

x86

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Shell32.dll

6.1.7600.20600

21,168,128

19-Dec-2009

08:15

IA-64

Shell32.dll

6.1.7600.20600

12,866,560

19-Dec-2009

09:10

x86

Workaround

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows To work around this issue, follow these steps to make a registry modification for all the domain users on the client computer that is running Windows 7 or Windows Server 2008 R2:

  1. Click Start the Start button , in the Search programs and files box, type regedit.exe.User Account Control permission If you are prompted for an administrator password or confirmation, type the password, or click Continue

  2. Locate the following registry subkey: HKEY_CURRENT_USER\Control Panel\Desktop

  3. Double-click the WALLPAPER registry entry. In the Value data box, type a value, such as c:\temp\wallpaper.jpg, and then click OK.

Note You can use Group Policy Preferences to apply this registry setting to multiple computers.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

How to apply a "Desktop Wallpaper" Group Policy setting

To apply a "Desktop Wallpaper" Group Policy setting, follow these steps:

  1. Open the Group Policy Management Console.

  2. In the Group Policy Management Console, locate the Group Policy Objects folder, and then select the Group Policy object (GPO) that you have created for the domain users. Note If you have not created a GPO for the domain users, right-click Group Policy Objects, and then click New to create a GPO for the domain users.

  3. Right-click the GPO that you have created for the domain users, and then click Edit to open the GPO.

  4. Expand User Configuration, expand Administrative Templates, expand Desktop, and then click Desktop.

  5. In the details pane, double-click Desktop Wallpaper.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File name

X86_caf7e6d7c2720074bdd2b6ddb3310166_31bf3856ad364e35_6.1.7600.20600_none_cd9b1f22855fd077.manifest

File version

File size

695

Date (UTC)

21-Dec-2009

Time (UTC)

02:38

Platform

Not Applicable

File name

X86_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.20600_none_6cda9f868c30bf0d.manifest

File version

File size

1,059,457

Date (UTC)

19-Dec-2009

Time (UTC)

09:35

Platform

Not Applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_4cd5c0925ee96076ee1e4c0b72f75abb_31bf3856ad364e35_6.1.7600.20600_none_71988414b3085a8f.manifest

File version

File size

1,040

Date (UTC)

21-Dec-2009

Time (UTC)

02:38

Platform

Not Applicable

File name

Amd64_a49df14782f9475226785e0493f0e87d_31bf3856ad364e35_6.1.7600.20600_none_bbe5e4c250a53a2d.manifest

File version

File size

699

Date (UTC)

21-Dec-2009

Time (UTC)

02:38

Platform

Not Applicable

File name

Amd64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.20600_none_c8f93b0a448e3043.manifest

File version

File size

1,058,443

Date (UTC)

19-Dec-2009

Time (UTC)

10:38

Platform

Not Applicable

File name

Wow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.20600_none_d34de55c78eef23e.manifest

File version

File size

1,054,916

Date (UTC)

19-Dec-2009

Time (UTC)

09:25

Platform

Not Applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_30b6364087bb07f5af862d5ed2f4b15b_31bf3856ad364e35_6.1.7600.20600_none_20bccb697e195501.manifest

File version

File size

1,038

Date (UTC)

21-Dec-2009

Time (UTC)

02:38

Platform

Not Applicable

File name

Ia64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.20600_none_6cdc437c8c2ec809.manifest

File version

File size

1,058,441

Date (UTC)

19-Dec-2009

Time (UTC)

10:05

Platform

Not Applicable

File name

Wow64_microsoft-windows-shell32_31bf3856ad364e35_6.1.7600.20600_none_d34de55c78eef23e.manifest

File version

File size

1,054,916

Date (UTC)

19-Dec-2009

Time (UTC)

09:25

Platform

Not Applicable

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.